Method and apparatus for controlling group affiliation for a user with multiple mobile devices

ABSTRACT

A communication system is provided for controlling group affiliation in a wireless communication system, wherein a group management server determines, or modifies, a set of one or more group affiliation parameters and group de-affiliation parameters associated with a mobile device based on capabilities of another mobile device and/or a set of one or more group affiliation parameters and group de-affiliation parameters associated with the another mobile device. The mobile devices may be mobile devices of a same user or may be mobile devices of different users. In other embodiments of the present invention, in response to receiving a request to initiate a group call involving a group that includes multiple mobile devices of a same user, the group management server may select only one of the multiple mobile devices to participate in the group call and arrange for only the selected mobile device to participate in the group call.

FIELD OF THE INVENTION

The present invention relates generally to wireless communicationsystems and, in particular, to group affiliation in association withprovisioning group services in a wireless communication system.

BACKGROUND OF THE INVENTION

Today, talkgroup affiliation is triggered by an end user deviceaffiliating to the talkgroup based on a pre-configuration of thetalkgroups or based on a user-defined talkgroup scanning list (forexample, in Land Mobile Radio (LMR) talkgroups communications). MotorolaPush-to-Talk (MPTT) supports an implicit affiliation of a client deviceto all talkgroups on a talkgroup list when the client registers with aPush-to-Talk (PTT) server. MPTT also supports the client deviceinforming the PTT server of the client device's scan list. When a useris using multiple client devices, there is the possibility that the usermay receive multiple audio streams via the multiple client devices aspart of a same talkgroup session, which wastes system bandwidth and airinterface resources and can result in confusion for the user. Further,when a user of a shared (among multiple users) mobile device, such as apolice radio, leaves the shared mobile device “on” at the end of theuser's shift, the shared mobile device remains affiliated to the user'stalkgroups even after the shift ends, thereby consuming resources in theuser's base site (for example, Multicast-Broadcast Single-FrequencyNetwork (MBSFN) resources).

Therefore, there is a need to provide an automated set ofaffiliation/de-affiliation procedures for PTT mobile devices.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

The accompanying figures, where like reference numerals refer toidentical or functionally similar elements throughout the separateviews, together with the detailed description below, are incorporated inand form part of the specification, and serve to further illustrateembodiments of concepts that include the claimed invention, and explainvarious principles and advantages of those embodiments.

FIG. 1 is a block diagram of a wireless communication system inaccordance with various embodiments of the present invention.

FIG. 2 is a block diagram of a mobile device in accordance with variousembodiments of the present invention.

FIG. 3 is a block diagram of a Group Management Server in accordancewith an embodiment of the present invention.

FIG. 4A is a logic flow diagram illustrating a method executed by thewireless communication system of FIG. 1 in controlling group affiliationin accordance with various embodiments of the present invention.

FIG. 4B is a continuation of the logic flow diagram of FIG. 4Aillustrating a method executed by the wireless communication system ofFIG. 1 in controlling group affiliation in accordance with variousembodiments of the present invention.

FIG. 5 is a logic flow diagram illustrating a method executed by thewireless communication system of FIG. 1 in controlling group affiliationin accordance with various embodiments of the present invention.

Skilled artisans will appreciate that elements in the figures areillustrated for simplicity and clarity and have not necessarily beendrawn to scale. For example, the dimensions and/or relative positioningof some of the elements in the figures may be exaggerated relative toother elements to help to improve understanding of various embodimentsof the present invention. Also, common but well-understood elements thatare useful or necessary in a commercially feasible embodiment are oftennot depicted in order to facilitate a less obstructed view of thesevarious embodiments of the present invention. It will further beappreciated that certain actions and/or steps may be described ordepicted in a particular order of occurrence while those skilled in theart will understand that such specificity with respect to sequence isnot actually required. Those skilled in the art will further recognizethat references to specific implementation embodiments such as“circuitry” may equally be accomplished via replacement with softwareinstruction executions either on general purpose computing apparatus(e.g., CPU) or specialized processing apparatus (e.g., DSP). It willalso be understood that the terms and expressions used herein have theordinary technical meaning as is accorded to such terms and expressionsby persons skilled in the technical field as set forth above exceptwhere different specific meanings have otherwise been set forth herein.

DETAILED DESCRIPTION OF THE INVENTION

A method and apparatus are provided for controlling group affiliation ina wireless communication system. The wireless communication systemincludes a group management server, which group management serverdetermines, or modifies, a set of one or more group affiliationparameters and group de-affiliation parameters associated with a mobiledevice based on capabilities of another mobile device and/or a set ofone or more group affiliation parameters and group de-affiliationparameters associated with the another mobile device. In variousembodiments of the present invention, the mobile devices may be mobiledevices associated with a same user or may be mobile devices associatedwith different users. In other embodiments of the present invention, inresponse to receiving a request to initiate a group call involving agroup that includes both a first and a second mobile device of a sameuser, the group management server may select only one of the first andsecond mobile devices to participate in the group call and arrange foronly the selected mobile device to participate in the group call.

Generally, an embodiment of the present invention encompasses a methodfor controlling group affiliation in a wireless communication system.The method includes receiving, by a group management server from asecond mobile device associated with a user, an affiliation request;determining, by the group management server, values for a second set ofone or more group affiliation parameters and group de-affiliationparameters for the second mobile device, wherein the second set of oneor more group affiliation parameters and group de-affiliation parametersconcern affiliation by the second mobile device with a set of groups andwherein the determination of the second set of one or more groupaffiliation parameters and group de-affiliation parameters is based onone or more of: a capability of a first mobile device associated withthe user; and one or more values of a first set of one or more groupaffiliation parameters and group de-affiliation parameters associatedwith the first mobile device. The method further includes, in responseto receiving the affiliation request, conveying, to the second mobiledevice, the second set of one or more group affiliation parameters andgroup de-affiliation parameters.

Another embodiment of the present invention encompasses a method forcontrolling group affiliation in a wireless communication system. Themethod includes receiving, by a Group Management Server, a request toinitiate a group call involving a group comprising a first mobile deviceand a second mobile device of a same user; selecting, by the GroupManagement Server, only one of the first mobile device and the secondmobile device to participate in the group call; and arranging, by theGroup Management Server, for only the selected mobile device of thefirst mobile device and the second mobile device to participate in thegroup call.

Yet another embodiment of the present invention encompasses an apparatusfor implementing a group call in a wireless communication system. Theapparatus includes a Group Management Server comprising a processor andan at least one memory device that is configured to store a set ofinstructions that, when executed by the processor, cause the processorto perform the following functions: receive, from a second mobile deviceassociated with a user, an affiliation request; determine for a secondset of one or more group affiliation parameters and group de-affiliationparameters for the second mobile device, wherein the second set of oneor more group affiliation parameters and group de-affiliation parametersconcern affiliation by the second mobile device with a set of groups andwherein the determination of the second set of one or more groupaffiliation parameters and group de-affiliation parameters is based onone or more of: a capability of a first mobile device associated withthe user; and one or more values of a first set of one or more groupaffiliation parameters and group de-affiliation parameters associatedwith the first mobile device. Further, the set of instructions, whenexecuted by the processor, cause the processor to, in response toreceiving the affiliation request, convey, to the second mobile device,the second set of one or more group affiliation parameters and groupde-affiliation parameters.

Still another embodiment of the present invention encompasses anapparatus for for implementing a group call in a wireless communicationsystem. The apparatus includes a Group Management Server comprising aprocessor and an at least one memory device that is configured to storea set of instructions that, when executed by the processor, cause theprocessor to perform the following functions: receive a request toinitiate a group call involving a group comprising a first mobile deviceand a second mobile device of a same user; select only one of the firstmobile device and the second mobile device to participate in the groupcall; and arrange for only the selected mobile device of the firstmobile device and the second mobile device to participate in the groupcall.

Yet another embodiment of the present invention encompasses a method forcontrolling group affiliation in a wireless communication system. Themethod includes receiving, by a group management server from a firstmobile device, a first affiliation request; in response to receiving thefirst affiliation request, conveying, to the first mobile device, afirst set of one or more group affiliation parameters and groupde-affiliation parameters. receiving, by a group management server froma second mobile device, a second affiliation request; in response toreceiving the second affiliation request, modifying the first set of oneor more group affiliation parameters and group de-affiliation parametersto produce a modified first set of one or more group affiliationparameters and group de-affiliation parameters; and conveying, to thefirst mobile device, the modified first set of one or more groupaffiliation parameters and group de-affiliation parameters.

The present invention may be more fully described with reference toFIGS. 1-5. FIG. 1 is a block diagram of a wireless communication system100 in accordance with various embodiments of the present invention.Communication system 100 includes one or more wireless communicationnetworks 120, 130 (two shown), such as a first network 120 and a secondnetwork 130. First network 120 comprises a first access network 122 incommunication with a first core network 126. First access network 122includes a first access node 124 that provides wireless communicationsservices to mobile devices residing in a coverage area of the accessnode via a first air interface 110. Second network 130 comprises asecond access network 132 in communication with a second core network134. Second access network 132 includes a second access node 134 thatprovides wireless communications services to mobile devices residing ina coverage area of the second access node via a second air interface112. Each of air interfaces 110 and 112 includes an uplink and adownlink, which uplinks and downlinks each includes multiple trafficchannels and multiple signaling channels.

In various embodiments of the present invention, each of the first andsecond networks 120, 130 may be a same or a different type of network.For example, each of the first and second networks 120, 130 may be abroadband network, each of the first and second networks 120, 130 may bea narrowband network, or one network of the first and second networks120, 130 may be a broadband network and the other network of the firstand second networks 120, 130 may be a narrowband network. For example,one of the multiple networks 120, 130 may be a narrowband network usedby a local agency or enterprise, such as a public safety organization,which narrowband network implements a specialized voice communicationsystem that typically supports low-bit-rate digital or analogtransmission of audio and/or data streams. An example of such anarrowband network is a network used by a Project 25 (P25)-compatibletwo-way Push-To-Talk voice communication system that includes wirelessand wired voice communication devices. Other examples include a LandMobile Radio (LMR) network or a Terrestrial Trunked Radio (TETRA) systemnetwork. Public safety organizations may choose these narrowband systemsbecause they provide improved end-to-end voice quality and efficientgroup communication, use advanced cryptography, enable centralizedlogging of calls, and/or are associated with lower delay and higherreliability. By way of further example, another of the multiple networks120, 130 may be a broadband network used, in parallel, by the publicsafety organization to support data applications or may be a commercialcarrier broadband network that supports users' personal devices (forexample, a ‘bring your own device’ (BYOD)). An example of such abroadband network is a network that operates in accordance with theThird Generation Partnership Project (3GPP) or 3GPP2 standards or theirnext generation standards, such as the 3GPP LTE (Long Term Evolution)standard wherein the core network is an evolved packet core (EPC).Broadband networks typically support high-bit-rate digital transmissionof data streams, including real-time video.

Communication system 100 further includes multiple mobile devices 104,106 (two shown) associated with a same user 102 and that each resideswithin a coverage area, such as a cell or a sector of a cell, of arespective network 120, 130 and that each is provided wireless serviceby a corresponding access node 124, 134 of their serving networks 120,130 via the corresponding air interface 110, 112. For example, a firstmobile device 104 of the multiple mobile devices 104, 106, may be anarrowband mobile device, for example, a portable narrowband two-wayradio, a land mobile radio (LMR), or other similar voice communicationentity, and a second mobile device 106 of the multiple mobile devices104, 106, may be a broadband mobile device, for example, a wirelesscommunication-enabled laptop, tablet, or personal digital assistant(PDA), a cellular telephone, or other similar communication entity.However, in some embodiments of the present invention, each of themultiple mobile devices 104, 106 may be served by a same network, suchas one of networks 120 and 130, and may be served by a same access nodeor by different access nodes of that network. Further, in someembodiments of the present invention, each of the multiple mobiledevices 104, 106 may be associated with a different user. Each of themultiple mobile devices 104, 106 maintains a respective scan list 105,107 that comprises a list of groups of which the mobile device is amember and whose signaling and traffic is monitored by the mobile devicewhen the mobile device is active in communication system 100.

Communication system 100 further includes a local agency or enterpriseservice network 150 that is remote to core network 126 and 136 and thatis accessible by mobile devices 104 and 106 via networks 120 and 130 anda data network 140, such as a private network or the Internet. Servicenetwork 150 includes one or more application functions (AFs), such as aGroup Management Server 152, for example, a Push-to-Talk (PTT) Serverand/or a Site Controller or Zone Controller, that reside above thehierarchical layers of core networks 126 and 136, which in turn resideabove the hierarchical layers of access networks 122 and 132. Further,service network 150 includes a group call database 162 and a userprofile database 164 that are each accessible by Group Management Server152. Access nodes 124 and 134, core networks 126 and 136, data network140, Group Management Server 152, and databases 162 and 164 collectivelycomprise an infrastructure of communication system 100 and,correspondingly, each may be referred to as an infrastructure element ofcommunication system 100.

Group Management Server 152 includes group call contact and callmanagement functionality 154 that controls group sessions of acommunication group, including managing talkgroups and group, or scan,lists (the terms ‘group list’ and ‘scan list’ are used interchangeablyherein) that are needed for provisioning group services, for example,maintaining identifiers of and contact information for members of atalkgroup. More particularly, group call contact and managementfunctionality 154 provides group list management functionality tocommunication system 100, for example, creating, modifying, retrievingand deleting communication groups, such as talkgroups, for authorizedusers, providing storage for talkgroups and lists in a group calldatabase 162 included in, or accessible by, Group Management Server 152,and providing notifications to authorized users of modifications to thecommunication groups and group lists. Each communication group includesa group identifier (ID), such as a talkgroup ID, that is uniquelyassociated with the communication group and, in association with thegroup ID, a list of member identifiers (IDs), such as mobile device IDs,for example, a Subscriber Unit ID (SUID), a Mobile Subscriber ISDNNumber (MSISDN) an International Mobile Equipment Identity (IMEI), or anInternational Mobile Subscriber Identity (IMSI), that uniquely identifyeach member of the communication group.

Group Management Server 152 further includes call control functionality156, registrar functionality 158, and one or more applications orservices 160, for example, a Push-to-Talk service or a videodistribution service. Call control functionality 156 performs callprocessing and allocates channels/resources for group calls. Registrarfunctionality 158 authenticates mobile devices, such as mobile devices104 and 106, when they register in communication system 100, and inparticular with Group Management Server 152, and binds a user to amobile device upon authentication of the mobile device. In otherembodiments of the present invention, one or more of call controlfunctionality 156 and registrar functionality 158 may be implemented byan infrastructure element, and in particular an element of servicenetwork 150, separate from, and accessible by, Group Management Server152.

User profile database 164 maintains a user profile for each user, suchas user 102, and mobile device, such as mobile devices 104 and 106,registered with communication system 100. For example, user profiledatabase 164 may maintain information concerning services subscribed toby a user, a public safety agency for which the user works, a roleand/or rank of the user at the public safety agency, and thecapabilities of, and services supported by, each mobile device, such aswhether the mobile device is a data-enabled mobile device or is avoice-only mobile device, vocoder capabilities of the mobile device, andwhether the mobile device supports multicast/broadcast services such asMultimedia Broadcast/Multicast Services (MBMS) or evolved MBMS (eMBMS)or other LTE multicast services such as SC-PTM (Single Cell Point toMultipoint).

Referring now to FIG. 2, a block diagram of a mobile device 200, such asmobile devices 104 and 106, is provided in accordance with variousembodiments of the present invention. Mobile device 200 may be, forexample, a smart phone, a land mobile radio (LMR), a vehicle modem, aserver mounted in vehicle, a tablet, a laptop, a body-worn computingdevice, etc. Mobile device 200 generally includes a processor 202, atleast one memory device 204, one or more input/output (I/O) interfaces210, and one or more wireless interfaces 212, 214 (two shown). It shouldbe appreciated by those of ordinary skill in the art that FIG. 2 depictsmobile device 200 in an oversimplified manner, and a practicalembodiment may include additional components and suitably configuredprocessing logic to support known or conventional operating featuresthat are not described in detail herein. The components (202, 204, 210,212, and 214) of mobile device 200 are communicatively coupled via alocal interface 216. Local interface 216 can be, for example but notlimited to, one or more buses or other wired or wireless connections, asis known in the art. Local interface 216 can have additional elements,which are omitted for simplicity, such as controllers, buffers (caches),drivers, repeaters, and receivers, among many others, to enablecommunications. Further, local interface 216 may include address,control, and/or data connections to enable appropriate communicationsamong the aforementioned components.

Mobile device 200 operates under the control of processor 202, such asone or more microprocessors, microcontrollers, digital signal processors(DSPs), combinations thereof or such other devices known to those havingordinary skill in the art. Processor 202 operates the correspondingmobile device according to data and instructions stored in the at leastone memory device 204, such as random access memory (RAM), dynamicrandom access memory (DRAM), and/or read only memory (ROM) orequivalents thereof, that stores data and instructions that may beexecuted by the corresponding processor so that the mobile device mayperform the functions described herein.

I/O interfaces 210 may include user interfaces that allow a user toinput information in, and receive information from, mobile device 200.For example, the user interfaces may include a keypad, a touch screen, ascroll ball, a scroll bar, buttons, bar code scanner, and the like.Further, the user interfaces may include a display device such as aliquid crystal display (LCD), touch screen, and the like for displayingsystem output. I/O interfaces 210 also can include, for example, aserial port, a parallel port, a small computer system interface (SCSI),an infrared (IR) interface, a universal serial bus (USB) interface, andthe like for communicating with, or coupling to, an external device.

The one or more wireless interfaces 212, 214 (two shown) facilitate anexchange wireless communications with other mobile devices and/or withan access network, such as access networks 122 and 132. For example, theone or more wireless interfaces 212, 214 may include a first,short-range wireless interface 212, such as a Bluetooth apparatus thatincludes a respective Bluetooth radio and antenna and/or a WLANapparatus that includes an WLAN transceiver and antenna, for short-rangecommunications with other mobile devices. Further, the one or morewireless interfaces 212, 214 may include a second, longer range wirelessinterface 214, such as a wireless area network (WAN) radio transceiverwith a corresponding antenna.

The data and instructions maintained by at least one memory device 204include software programs that include an ordered listing of executableinstructions for implementing logical functions. For example, thesoftware in at least one memory device 204 includes a suitable operatingsystem (O/S) and programs. The operating system essentially controls theexecution of other computer programs, and provides scheduling,input-output control, file and data management, memory management, andcommunication control and related services. The programs may includevarious applications, add-ons, etc. configured to provide userfunctionality with mobile device 200, for example, at least one memorydevice 204 maintains a group call client 206 that, when executed byprocessor 202, facilitates a peer-to-peer exchange of signaling andtraffic with Group Management Server 152. At least one memory device 204further maintains at least one identifier (ID) of the mobile device,such as a subscriber unit identifier (SUID), an IMEI, an MSISDN, anIMSI, and/or a SIP URI, that uniquely identifies the mobile device incommunication system 100.

Additionally, at least one memory device 204 maintains a scan list 208,such as scan lists 105 and 107, which scan list comprises a list ofcommunication groups, such as talkgroups, of which the mobile device isa member and which groups are monitored by the mobile device foron-going or new group calls. For example, scan list 208 may comprise alist of group IDs that are each uniquely associated with a communicationgroup of which the mobile device is a member. The group IDs may bepreprogrammed into at least one memory device 204, may be synchronizedto the mobile device and stored in at least one memory device 204 whenthe mobile device registers with Group Management Server 152 and/or maybe input to at least one memory device 204 by a user of the mobiledevice. Further, as described herein, entries in scan list 208 may bemodified by Group Management Server 152 through a use of groupaffiliation and deaffiliation parameters.

Referring now to FIG. 3, a block diagram is provided of Group ManagementServer 152 in accordance with an embodiment of the present invention.Group Management Server 152 includes a processor 302, such as one ormore microprocessors, microcontrollers, digital signal processors(DSPs), combinations thereof or such other devices known to those havingordinary skill in the art. Group Management Server 152 further includesan at least one memory device 304, such as random access memory (RAM),dynamic random access memory (DRAM), and/or read only memory (ROM) orequivalents thereof, that is in communication with a correspondingprocessor 302, via a corresponding local interface 308, 408. At leastone memory device 304 stores data and programs, such as group callprograms, that may be executed by processor 302 and that allows theGroup Management Server to perform all functions necessary to operate incommunication system 100, such as instructions for implementing groupcall contact and management functionality 154, call controlfunctionality 156, registrar functionality 158, and the one or moreapplications and services 160.

Group Management Server 152 further includes one or more networkinterfaces 306 (one shown) that is in communication with processor 302via a local interface 308 and that provides for interfacing with otherinfrastructure devices of communication system 100, such as data network140 and databases 162 and 164. Local interface 308 can be, for examplebut not limited to, one or more buses or other wired or wirelessconnections, as is known in the art. Local interface 308 can haveadditional elements, which are omitted for simplicity, such ascontrollers, buffers (caches), drivers, repeaters, and receivers, amongmany others, to enable communications. Further, local interface 308 mayinclude address, control, and/or data connections to enable appropriatecommunications among the aforementioned components of the GroupManagement Server.

In order to conserve system bandwidth when a user having multipleactivated client (mobile) devices is engaging in a group communicationsession, and to prevent confusion for the user when each of the multipleactivated client devices is playing out the same audio as part of thegroup communication session, communication system 100 provides for GroupManagement Server 152 to automatically select which of the multipleclient devices will participate in the session, that is, a selectedclient device, and to prevent the other, non-selected, activated clientdevices from participating in the session. Thus, system bandwidth isconserved as traffic channels will not be set up for the non-selectedclient devices and further confusion is minimized for the user as asingle client device may be selected to play out audio for the session.Further, in selecting which client device of the multiple client deviceswill participate in the session, Group Management Server 152 mayconsider attributes of each client device of the multiple activatedclient devices, so that an optimal client device may be selected toparticipate in the session.

Referring now to FIGS. 4A and 4B, a logic flow diagram 400 is providedthat illustrates a method performed by communication system 100 incontrolling group affiliation, and thereby group communication sessionparticipation, in accordance with various embodiments of the presentinvention. Logic flow diagram 400 begins (402) when a first mobiledevice, such as mobile device 104, of the multiple mobile devices 104,106 of user 102 registers (404) with a network serving the mobiledevice, such as network 120 with respect to mobile device 104, and withservice network 150 in accordance with well-known techniques. Forexample, mobile device 104 may activate in communication system 100 and,in response to activating in communication system 100, register withnetwork 120 and service network 150.

As part of the process of registering with service network 150, firstmobile device 104 authenticates (406) with Group Management Server 152and affiliates with Group Management Server 152, that is, conveys afirst group affiliation request and associated first group affiliationinformation to the Group Management Server, and in particular to groupcall contact and management functionality 154. The first groupaffiliation information includes an identifier of the mobile device,such as an SUID, an IMEI, an MSISDN, and/or an IMSI, an identifier of auser of the mobile device, that is, user 102, such as a name of the userand/or a badge number of the user, and information concerning any groupswith which the mobile device/user is associated, such as a groupidentifier (ID), for example, a talkgroup ID. For example, and merelyfor the purpose of illustrating the principles of the present invention,it is assumed herein that mobile device 104 is a member of each group ofa first set of groups, which first set of groups includes a Group ‘A’and a Group ‘B,’ and that mobile device 106 is a member of each group ofa second set of groups, which second set of groups includes Group A andfurther includes a Group ‘C.’ That is, the first set of groups and thesecond set of groups overlap and may or may not be the same. In responseto receiving the first affiliation information from first mobile device104 (including identifiers of a user, such as user 102, of mobile device104, and of the groups of which mobile device 104 is a member, that is,Groups A and B), Group Management Server 152, and in particular groupcall contact and management functionality 154, binds the mobile deviceidentifier to the user identifier, associated with mobile identifier anduser identifier with the group identifiers, and compiles the affiliationinformation into a table maintained by the at least one memory device304 of the Group Management Server.

Further, in response to receiving the first group affiliation requestand associated first group affiliation information from mobile device104, Group Management Server 152, and in particular group call contactand management functionality 154, determines and stores (408), byreference to user profile database 164, a user profile associated with,and capabilities of, first mobile device 104 and further determines andstores values for a first set of one or more group affiliationparameters and group de-affiliation parameters in association with firstmobile device 104. The first set of one or more groupaffiliation/de-affiliation parameters comprises a subset of one or moregroup affiliation/de-affiliation parameters for each of one or moregroups to which the first mobile device 104 belongs, that is, for one ormore groups of the first set of groups. For example, the first set ofone or more group affiliation/de-affiliation parameters may include afirst subset of one or more group affiliation/de-affiliation parametersthat are applicable to Group A and a second subset of one or more groupaffiliation/de-affiliation parameters that are applicable to Group B, orthe first set of one or more group affiliation/de-affiliation parametersmay include a single subset of one or more groupaffiliation/de-affiliation parameters that are applicable to both GroupA and Group B, or the first set of one or more groupaffiliation/de-affiliation parameters may include a subset of groupaffiliation/de-affiliation parameters that are applicable to both GroupA and Group B and subsets of group affiliation/de-affiliation parametersthat are applicable to only Group A or to only Group B.

A first group affiliation/de-affiliation parameter of the set of one ormore group affiliation/de-affiliation parameters is a ‘group attachmentlifetime’ parameter that identifies a lifetime of a group attachment,that is, a time period upon whose expiration the mobile device'sattachment to a given group will expire. The group attachment lifetimemay be the same for all groups to which the mobile device affiliates,that is, Groups A and B with respect to mobile device 104, or may beindividually set for each group. For example, a value for the groupattachment lifetime parameter may be ‘infinite,’ or ‘open ended,’wherein the mobile device/user will be affiliated with the group for thelifetime of the group. By way of another example, the group attachmentlifetime parameter may have a ‘limited duration’ value, specifying aperiod of time during which the mobile device/user will remain attachedwith the group, for example, a number of minutes, hours, or days, duringwhich the mobile device/user will remain attached to the group and afterwith the mobile device/user's attachment to the group will expire, orspecifying a time at which the mobile device/user's attachment to thegroup will expire.

A second group affiliation/de-affiliation parameter of the subset of oneor more group affiliation/de-affiliation parameters is a ‘groupaffiliation frequency’ parameter. The group affiliation frequencyparameter indicates a frequency with which, that is, how often, themobile device should affiliate to each of one or more groups of which itis a member, that is, Groups A and B with respect to mobile device 104.For example, a value for a group affiliation frequency parameter may be‘daily,’ ‘weekly,’ ‘weekdays,’ or ‘upon a next reset of the mobiledevice.’

A third group affiliation/de-affiliation parameter of the subset of oneor more group affiliation/de-affiliation parameters is an‘auto-affiliation’ parameter. The auto-affiliation parameter indicateswhether the mobile device will be automatically affiliated to one ormore of groups of which the mobile device is a member each time themobile device registers with Group Management Server 152, that is, toone or more of Groups A and B with respect to mobile device 104. Thatis, the auto-affiliation parameter indicates, for a given groupassociated with user 102, such as Group A, whether Group ManagementServer 152 will automatically affiliate the mobile device with Group Awhenever the mobile device registers with the Group Management Server.Correspondingly, each time the device 104 registers with the GroupManagement Server, the mobile device 104 automatically includes, in itsscan list 105, each group identified by the ‘auto-affiliation’parameter. For example, the ‘auto-affiliation’ parameter may indicatethat mobile device 104 will be automatically affiliated with Group A,but not Group B, each time the mobile device registers with GroupManagement Server 152. As a result, when mobile device 104 affiliateswith Group Management Server 152, the mobile device affiliates withGroup A but does not affiliate with Group B.

A fourth group affiliation/de-affiliation parameter of the subset of oneor more group affiliation/de-affiliation parameters is a‘de-affiliation’ parameter. The de-affiliation parameter comprises alist of one or more groups of which the mobile device is a member andwith respect to which the mobile device is to de-affiliate. That is, thede-affiliation parameter identifies one or more groups that are to beautomatically removed from a scan list of the mobile device. Therefore,when mobile device 104 receives a ‘de-affiliation’ parameter identifyingone or more of the groups on the mobile device's scan list 105, such asone or more of Groups A and B, the mobile device automatically removes,from scan list 105, all such groups identified by the ‘de-affiliation’parameter.

A fifth group affiliation/de-affiliation parameter of the subset of oneor more group affiliation/de-affiliation parameters is a ‘selectedtalkgroup’ parameter. The selected talkgroup parameter identifies agroup that is automatically set to the priority talk group of the mobiledevice, overriding the priority talkgroup currently selected by theuser. Subsequent PTT communication will result in communication to thenew selected talkgroup. At any given instant of time, only one group ischosen as the ‘selected talkgroup.’

Group Management Server 152 then conveys (410), to mobile device 104,the first set of one or more group affiliation/de-affiliationparameters. For example, Group Management Server 152 may convey thefirst set of one or more group affiliation/de-affiliation parameters byuse of vCard, as described by the Open Mobile Alliance DataSynchronization [OMA-DS], which provides a Converged Address Book (CAB)Enabler that provides a mechanism for managing list synchronizationbetween a network-based server, such as Group Management Server 152, anda client of a mobile device, such as group call client 206 of mobiledevice 104. By way of another example, Group Management Server 152 mayconvey the one or more group affiliation/de-affiliation parameters byuse of Session Initiation Protocol (SIP) messaging. By way of yetanother example, Group Management Server 152 may convey the one of moregroup affiliation/de-affiliation parameters by use of Open MobileAlliance XML Document Management enabler's XCAP protocol.

In response to receiving the first set of one or more groupaffiliation/de-affiliation parameters, first mobile device 104 modifies(412) a group entry for each group listed in a first scan list, that is,scan list 105, maintained by the first mobile device, such as Groups Aand B, to reflect the subset of one or more groupaffiliation/de-affiliation parameters received with respect to thatgroup. For example, based on the ‘group attachment lifetime’ parameter,mobile device 104 may indicate, in scan list 105, an identified lifetimeof an attachment to that group; based on the ‘group affiliationfrequency’ parameter, mobile device 104 may indicate, in scan list 105,how often the mobile device needs to affiliate to that group; based onthe ‘auto-affiliation’ parameter, mobile device 104 automaticallyincludes the group in scan list 105 each time the mobile deviceregisters with Group Management Server 152; based on the‘de-affiliation’ parameter, mobile device 104 automatically removes thegroup from scan list 105; and based on the ‘selected talkgroup’parameter, mobile device 104 automatically changes the selected talkgroup or priority talk group of the device.

Concurrent with, or subsequent to, mobile device 104 affiliating withGroup Management Server 152, a second mobile device, such as mobiledevice 106, of the multiple mobile devices 104, 106 of user 102registers (414) with a network serving the mobile device, such asnetwork 130 with respect to mobile device 106, and with service network150. As part of the process of registering with service network 150,mobile device 104 authenticates (416) with Group Management Server 152and affiliates with the Group Management Server, that is, conveys asecond group affiliation request and associated second group affiliationinformation to Group Management Server 152, and in particular to groupcall contact and management functionality 154. As described above, suchgroup affiliation information may include an identifier of the mobiledevice, such as an SUID, an IMEI, an MSISDN, and/or an IMSI, anidentifier of a user of the mobile device, that is, user 102, such as aname of the user and/or a badge number of the user, and informationconcerning any groups with which the mobile device/user is associated,such as a group identifier (ID), for example, a talkgroup ID. Inresponse to receiving the second group affiliation information fromsecond mobile device 106 (including identifiers of a user of mobiledevice 106 and of the groups of which mobile device 106 is a member,that is, Groups A and C), Group Management Server 152, and in particulargroup call contact and management functionality 154, binds the mobiledevice identifier to the user identifier, associated with mobileidentifier and user identifier with the group identifiers, and compilesthe affiliation information into a table maintained by the at least onememory device 304 of the Group Management Server.

Further, in response to receiving the second affiliation informationfrom second mobile device 106, Group Management Server 152 determinesand stores (418), by reference to user profile database 164, a userprofile associated with, and capabilities of, second mobile device 106and further determines and stores values for a second set of one or moregroup affiliation parameters and group de-affiliation parameters formobile device 106. Group Management Server 152 determines the second setof one or more group affiliation/de-affiliation parameters based on theprofile and capabilities associated with second mobile device 106 andfurther based on one or more of capabilities of other mobile devices ofthe same user 102 that are also affiliated with Group Management Server152, that is, in this instance, first mobile device 104, and the sets ofone or more group affiliation/de-affiliation parameters determined forsuch other mobile devices, in this instance the first set of one or moregroup affiliation/de-affiliation parameters determined for first mobiledevice 104. Similar to the first set of one or more groupaffiliation/de-affiliation parameters, the second set of groupaffiliation/de-affiliation parameters comprises a subset of one or moregroup affiliation/de-affiliation parameters for one or more groups towhich the second mobile device 106 belongs, that is, the second set ofgroups comprising Groups A and C, such as a ‘group attachment lifetime’parameter, a ‘group affiliation frequency’ parameter, an‘auto-affiliation’ parameter, a ‘de-affiliation’ parameter, and a‘selected talkgroup’ parameter.

For example, for a given group that is included in both the first set ofgroups (associated with mobile device 104) and the second set of groups(associated with mobile device 106), such as Group A, Group ManagementServer 152 may determine to set a value of one or more groupaffiliation/de-affiliation parameters applicable to Group A in thesecond set of one or more group affiliation/de-affiliation parameters tothe same value as was set for that group affiliation/de-affiliationparameter, with respect to Group A, in the first set of one or moregroup affiliation/de-affiliation parameters. By way of another example,Group Management Server 152 may determine to set a value of one or moregroup affiliation/de-affiliation parameters applicable to Group A in thesecond set of one or more group affiliation/de-affiliation parameters toa different value as was set for that group affiliation/de-affiliationparameter, with respect to Group A, in the first set of one or moregroup affiliation/de-affiliation parameters.

For example, if a group attachment lifetime parameter for mobile device104 has a lengthy value, for example, a week or weeks, then a value ofthe group attachment lifetime parameter for mobile device 106 may bemuch shorter, that is, an affiliation of mobile device 106 with Group Amay be considered more discretionary for the user in that the user isalready affiliated with Group A via mobile device 104. Similarly, if agroup affiliation frequency parameter for mobile device 104 has alengthy value, for example, wherein the mobile device need re-affiliateonly every week, then a group affiliation frequency parameter for mobiledevice 106 may be of a much higher frequency, for example, daily, as,again, an affiliation of mobile device 106 with Group A may beconsidered more discretionary for the user in that the user is alreadyaffiliated with Group A via mobile device 104 for a lengthier period oftime. By way of still another example, Group Management Server 152 maydetermine, based on the capabilities and services supported by each ofmobile devices 104 and 106, that one of mobile device 104 and 106 isbetter matched to a communication session involving Group A and,correspondingly, set a value for the de-affiliation parameter for theother mobile device, of mobile device 104 and 106, that instructs theother mobile device to de-affiliate from Group A. For example, one ofmobile device 104 and 106 may support multicast services (such as MBMSor eMBMS or SC-PTM) and the other mobile device may not, whereinmulticast service is the preferred scheme for a current or anticipatedcommunication session involving that group. In another example, one ofmobile devices 104 and 106 may support a vocoder that is more commonlyshared among the other members of Group A than the vocoders supportedthe other mobile device of mobile devices 104 and 106, which vocoder isa currently being used or is anticipated to be used in communicationsession involving that group. One may note that by utilizing a samevocoder at different mobile devices that are members of a same group,the infrastructure of communication system 100 may have to perform lessinterworking of communications among the mobile devices. In yet anotherexample, mobile devices 104 and 106 may have different securecommunication capabilities, where Group Management Server 152 may chooseto de-affiliate mobile devices from a group that are not capable ofsecure communication using a certain level of security (e.g., hardwareencryption or software encryption or clear calls).

Group Management Server 152 then conveys (420), to second mobile device106, the second set of group affiliation/de-affiliation parameters. Inresponse to receiving the second set of group affiliation/de-affiliationparameters, second mobile device 106 modifies (422) a group entry foreach group listed in a second scan list, that is, scan list 107,maintained by the second mobile device to reflect the subset of one ormore group affiliation/de-affiliation parameters received with respectto that group. Logic flow 400 then ends (430).

In some embodiments, in response to receiving affiliation informationfrom second mobile device 106, Group Management Server 152 further maydetermine (424) to modify the first set of one or more groupaffiliation/de-affiliation parameters associated with the first mobiledevice to produce a modified first set of one or more groupaffiliation/de-affiliation parameters. Group Management Server 152 thenmay convey (426), to first mobile device 104, the modified first set ofgroup affiliation/de-affiliation parameters. In response to receivingthe modified first set of group affiliation/de-affiliation parameters,first mobile device 104 modifies (428) a group entry for each grouplisted in the first scan list, that is, scan list 105, maintained by thefirst mobile device to reflect the modified first set of groupaffiliation/de-affiliation parameters received with respect to thatgroup, and logic flow 400 then ends (430).

For example, second mobile device 106 may be a preferred mobile device,as between mobile devices 104 and 106, for participating in groupcommunications involving multicast services or a particular type ofvocoding, where such multicast services or vocoding type is currentlybeing used or is anticipated to be used in communication sessioninvolving a given group. In another example, mobile devices 104 and 106may have different secure communication capabilities and by using secondmobile device 106 (as opposed to first mobile device 104) for a groupcommunication involving a given group, that group may be able to engagein a secure communication using a higher level of security. Accordingly,Group Management Server 152 may determine to modify a ‘selectedtalkgroup’ parameter or an ‘auto-affiliation’ parameter of first mobiledevice 104 in response to receiving the affiliation information fromsecond mobile device 106. In yet other examples, Group Management Server152 may determine to modify a group attachment lifetime parameter, agroup affiliation frequency parameter, or a de-affiliation parameter offirst mobile device 104 in response to receiving the affiliationinformation from second mobile device 106, for example and as notedabove, lengthening of shortening the group attachment lifetime parameteror the group affiliation frequency parameter or reversing ade-affiliation parameter based on a group attachment lifetime parameter,a group affiliation frequency parameter, or a de-affiliation parameterdetermined for second mobile device 106.

Referring now to FIG. 5, a logic flow diagram 500 is provided that thatillustrates a method performed by communication system 100 incontrolling group affiliation in accordance with various embodiments ofthe present invention. It is assumed herein, with respect to logic flowdiagram 500, that each of the multiple mobile device 104, 106 of user102 has activated in communication system 100 and is registered withGroup Management Server 152.

Logic flow diagram 500 begins (502) when Group Management Server 152receives (504) a request to originate a group call for a group thatincludes a plurality of the mobile devices of user 102, that is, bothfirst mobile device 104 and second mobile device 106. For example, thegroup call request may include a group ID that is included in the scanlists 105, 107 of both mobile device 104 and mobile device 106, or thegroup call request may include a list of mobile devices identifiers thatincludes the identifiers of both mobile device 104 and mobile device106.

In one embodiment of the present invention, in response to receiving thegroup call request at step 504, Group Management Server 152 may notify(506) each of mobile devices 104 and 106 of the group call. For example,Group Management Server 152 may convey a group call session invitationto each of mobile devices 104 and 106 via networks 120 and 130,respectively, or the Group Management Server may broadcast anotification of the group call via networks 120 and 130. In response tobeing notified of the group call, each of mobile devices 104 and 106notifies (508) Group Management Server 152 of the mobile device'sacceptance of the group call.

In response to receiving an acceptance of the group call from each ofmobile device 104 and 106 at step 508, Group Management Server 152selects (510) a mobile device of the plurality of the mobile devices ofuser 102 to participate in the group call, that is, selects one ormobile devices 104 and 106 to produce a selected mobile device, andarranges (512) for only the selected mobile device to participate in thegroup call. For example, if Group Management Server 152 selects mobiledevice 104 to participate in the group call, the Group Management Servermay terminate the participation of non-selected mobile device 106 byconveying a session ended, session termination, or session disconnectmessage to non-selected mobile device 106, such as a Session InitiationProtocol (SIP) BYE message or a Transmission Control Protocol/InternetProtocol (TCP/IP) disconnect message. By way of another example, theGroup Management Server may terminate the participation of non-selectedmobile device 106 by conveying a ‘de-affiliation’ parameter to mobiledevice 106 that instructs mobile device 106 to de-affiliate from thegroup and remove the group from its scan list. Logic flow 500 then ends(518).

In selecting a mobile device of the multiple mobile devices of user 102to participate in the group call, Group Management Server 152 mayconsider factors such as device capabilities, transceiving performancecharacteristics, and system efficiency. For example, by reference touser profile database 164, Group Management Server 152 may determinethat a mobile device of the multiple mobile devices 104 and 106 isdata-enabled and another mobile device is a voice-only mobile device,and may select the data-enabled or voice-only mobile device as isappropriate for the group call. For example, if the group call willinvolve a video transmission, Group Management Server 152 may select thedata-enabled mobile device, whereas if the group call is merely a voicecall, the Group Management Server may select the voice-only mobiledevice. By way of another example, Group Management Server 152 mayselect a mobile device that supports a vocoder that will be used for thegroup call and/or that is most widely supported by the other mobiledevices that will be participating in the group call. By way of yetanother example, if MBMS services are available for the group call,Group Management Server 152 may select an MBMS-enabled mobile device toavoid having to set up, and consume extra bandwidth for, a unicastdownlink transmission to a non-MBMS enabled mobile device. By way ofstill another example, Group Management Server 152 may select a mobiledevice served by a network, such as network 120 or network 130, with thegreatest available bandwidth, that provides the lowest cost of service,or that provides the highest level of security, for example, selecting amobile device operating on a private network of a public safety agencyas opposed to a mobile device, such as a BYOD (Bring your Own Device),operating over the network of a commercial carrier. By way of yetanother example, Group Management Server 152 may select a mobile devicehaving a best transceiving performance characteristic. For example, eachaccess network 122, 124 serving one or more of the multiple mobiledevices of a user may provide, to the Group Management Server,transceiving performance characteristics such as a signal strength (suchas received signal strength indication (RSSI)) or a signal quality (suchas signal-to-noise ratio (SNR), a signal-to-noise plus interferenceratio (SNR), a carrier-to-interference-plus-noise ratio (CINR), a bitenergy-to-noise density ratio (Eb/Io), a bit error rate, or a frameerror rate) associated with a signal conveyed to, or received from, eachof one or more of the multiple mobile devices of the user. The GroupManagement Server then may select a mobile device having a besttransceiving performance characteristic.

In another embodiment of the present invention, in response to receivingthe group call request at step 504, Group Management Server 152 GroupManagement Server 152 may select (514) a mobile device of the pluralityof the mobile devices of user 102, that is, select one of mobile device104 and 106, to participate in the group call prior to inviting each ofthe multiple mobile devices 104, 106 to participate in the group call.Again, in selecting a mobile device of the multiple mobile devices ofuser 102 to participate in the group call, Group Management Server 152may consider factors such as device capabilities, transceivingperformance characteristics, and system efficiency. Group ManagementServer 152 then arranges (516) for only the selected mobile device, forexample, mobile device 104, to participate in the group call. Forexample, Group Management Server 152 may notify only the selected mobiledevice, that is, mobile device 104, of the group call, so that only theselected mobile device participates in the group call. Logic flow 500then ends (518).

The embodiments of the present invention preferably are implementedwithin each of mobile devices 104 and 106 and Group Management Server152, and more particularly with or in software programs and instructionsstored in the at least one memory devices 204, 304 and executed by theprocessors 202, 302 of the mobile devices and Group Management Server.However, one of ordinary skill in the art realizes that the embodimentsof the present invention alternatively may be implemented in hardware,for example, integrated circuits (ICs), application specific integratedcircuits (ASICs), and the like, such as ASICs implemented in one or moreof mobile devices 104 and 106 and Group Management Server 152 and allreferences to ‘means for’ herein may refer to any such implementation ofthe present invention. Based on the present disclosure, one skilled inthe art will be readily capable of producing and implementing suchsoftware and/or hardware without undo experimentation.

In the foregoing specification, specific embodiments have beendescribed. However, one of ordinary skill in the art appreciates thatvarious modifications and changes can be made without departing from thescope of the invention as set forth in the claims below. Accordingly,the specification and figures are to be regarded in an illustrativerather than a restrictive sense, and all such modifications are intendedto be included within the scope of present teachings.

The benefits, advantages, solutions to problems, and any element(s) thatmay cause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as a critical, required, or essentialfeatures or elements of any or all the claims. The invention is definedsolely by the appended claims including any amendments made during thependency of this application and all equivalents of those claims asissued.

Moreover in this document, relational terms such as first and second,top and bottom, and the like may be used solely to distinguish oneentity or action from another entity or action without necessarilyrequiring or implying any actual such relationship or order between suchentities or actions. The terms “comprises,” “comprising,” “has,”“having,” “includes”, “including,” “contains,” “containing,” or anyother variation thereof, are intended to cover a non-exclusiveinclusion, such that a process, method, article, or apparatus thatcomprises, has, includes, contains a list of elements does not includeonly those elements but may include other elements not expressly listedor inherent to such process, method, article, or apparatus. An elementproceeded by “comprises . . . a,” “has . . . a,” “includes . . . a,”“contains . . . a” does not, without more constraints, preclude theexistence of additional identical elements in the process, method,article, or apparatus that comprises, has, includes, contains theelement. The terms “a” and “an” are defined as one or more unlessexplicitly stated otherwise herein. The terms “substantially,”“essentially,” “approximately,” “about,” or any other version thereof,are defined as being close to as understood by one of ordinary skill inthe art, and in one non-limiting embodiment the term is defined to bewithin 10%, in another embodiment within 5%, in another embodimentwithin 1% and in another embodiment within 0.5%. The term “coupled” asused herein is defined as connected, although not necessarily directlyand not necessarily mechanically. A device or structure that is“configured” in a certain way is configured in at least that way, butmay also be configured in ways that are not listed.

It will be appreciated that some embodiments may be comprised of one ormore generic or specialized processors (or “processing devices”) such asmicroprocessors, digital signal processors, customized processors andfield programmable gate arrays (FPGAs) and unique stored programinstructions (including both software and firmware) that control the oneor more processors to implement, in conjunction with certainnon-processor circuits, some, most, or all of the functions of themethod and/or apparatus described herein. Alternatively, some or allfunctions could be implemented by a state machine that has no storedprogram instructions, or in one or more application specific integratedcircuits (ASICs), in which each function or some combinations of certainof the functions are implemented as custom logic. Of course, acombination of the two approaches could be used. Both the state machineand ASIC are considered herein as a “processing device” for purposes ofthe foregoing discussion and claim language.

Moreover, an embodiment can be implemented as a computer-readablestorage element or medium having computer readable code stored thereonfor programming a computer (e.g., comprising a processing device) toperform a method as described and claimed herein. Examples of suchcomputer-readable storage elements include, but are not limited to, ahard disk, a CD-ROM, an optical storage device, a magnetic storagedevice, a ROM (Read Only Memory), a PROM (Programmable Read OnlyMemory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM(Electrically Erasable Programmable Read Only Memory) and a Flashmemory. Further, it is expected that one of ordinary skill,notwithstanding possibly significant effort and many design choicesmotivated by, for example, available time, current technology, andeconomic considerations, when guided by the concepts and principlesdisclosed herein will be readily capable of generating such softwareinstructions and programs and ICs with minimal experimentation.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various embodiments for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separately claimed subject matter.

What is claimed is:
 1. A method for controlling group affiliation in awireless communication system, the method comprising: receiving, by agroup management server from a second mobile device associated with auser, an affiliation request; determining, by the group managementserver, values for a second set of one or more group affiliationparameters and group de-affiliation parameters for the second mobiledevice, wherein the second set of one or more group affiliationparameters and group de-affiliation parameters concern affiliation bythe second mobile device with a set of groups and wherein thedetermination of the second set of one or more group affiliationparameters and group de-affiliation parameters is based on one or moreof: a capability of a first mobile device associated with the user; andone or more values of a first set of one or more group affiliationparameters and group de-affiliation parameters associated with the firstmobile device; and in response to receiving the affiliation request,conveying, to the second mobile device, the second set of one or moregroup affiliation parameters and group de-affiliation parameters.
 2. Themethod of claim 1, wherein the second set of one or more groupaffiliation parameters and group de-affiliation parameters comprises oneor more of: a group attachment lifetime parameter that identifies alifetime of a group attachment of the second mobile device to one ormore groups of the set of groups; a group affiliation frequencyparameter that indicates a frequency with which the second mobile deviceshould affiliate to one or more groups of the set of groups; anauto-affiliation parameter that indicates whether the second mobiledevice will be automatically affiliated to one or more of groups of theset of groups; a de-affiliation parameter that identifies one or moregroups of the set of groups from which the second mobile device is tode-affiliate; and a selected talkgroup parameter that identifies a groupthat will be set as the current talk group by the second mobile device.3. The method of claim 1, wherein the method further comprises:receiving, by the second mobile device, the second set of one or moregroup affiliation parameters and group de-affiliation parameters; andmodifying, by the second mobile device, a scan list maintained by thesecond mobile device based on the second set of one or more groupaffiliation parameters and group de-affiliation parameters.
 4. Themethod of claim 3, wherein modifying the scan list comprises deleting agroup from the scan list.
 5. The method of claim 4, wherein a scan listof the first mobile device comprises the group deleted from the scanlist of the second mobile device.
 6. The method of claim 1, wherein theset of groups is a second set of groups, wherein the affiliation requestis a second affiliation request, and wherein the method furthercomprises: receiving, by the group management server from the firstmobile device, a first affiliation request; determining, by the groupmanagement server, the first set of one or more group affiliationparameters and group de-affiliation parameters, wherein the first set ofone or more group affiliation parameters and group de-affiliationparameters are associated with a first set of groups and wherein thefirst set of groups and the second set of groups have at least one groupin common; and in response to receiving the first affiliation request,conveying, to the first mobile device, the first set of one or moregroup affiliation parameters and group de-affiliation parameters.
 7. Amethod for controlling group affiliation in a wireless communicationsystem, the method comprising: receiving, by a Group Management Server,a request to initiate a group call involving a group comprising a firstmobile device and a second mobile device of a same user; selecting, bythe Group Management Server, only one of the first mobile device and thesecond mobile device to participate in the group call; and arranging, bythe Group Management Server, for only the selected mobile device of thefirst mobile device and the second mobile device to participate in thegroup call.
 8. The method of claim 7, wherein arranging for only theselected mobile device to participate in the group call comprises:notifying only the selected mobile device, of the first mobile deviceand the second mobile device, of the group call.
 9. The method of claim7, further comprising: notifying the first mobile device and the secondmobile device of the group call; and wherein arranging for only theselected mobile device to participate in the group call comprisesterminating a participation of a non-selected mobile device of the firstmobile device and the second mobile device.
 10. An apparatus forimplementing a group call in a wireless communication system, theapparatus comprising: a Group Management Server comprising: a processor;and an at least one memory device that is configured to store a set ofinstructions that, when executed by the processor, cause the processorto perform the following functions: receive, from a second mobile deviceassociated with a user, an affiliation request; determine for a secondset of one or more group affiliation parameters and group de-affiliationparameters for the second mobile device, wherein the second set of oneor more group affiliation parameters and group de-affiliation parametersconcern affiliation by the second mobile device with a set of groups andwherein the determination of the second set of one or more groupaffiliation parameters and group de-affiliation parameters is based onone or more of: a capability of a first mobile device associated withthe user; and one or more values of a first set of one or more groupaffiliation parameters and group de-affiliation parameters associatedwith the first mobile device; and in response to receiving theaffiliation request, convey, to the second mobile device, the second setof one or more group affiliation parameters and group de-affiliationparameters.
 11. The apparatus of claim 10, wherein the second set of oneor more group affiliation parameters and group de-affiliation parameterscomprises one or more of: a group attachment lifetime parameter thatidentifies a lifetime of a group attachment of the second mobile deviceto one or more groups of the set of groups; a group affiliationfrequency parameter that indicates a frequency with which the secondmobile device should affiliate to one or more groups of the set ofgroups; an auto-affiliation parameter that indicates whether the secondmobile device will be automatically affiliated to one or more of groupsof the set of groups; a de-affiliation parameter that identifies one ormore groups of the set of groups from which the second mobile device isto de-affiliate; and a selected talkgroup parameter that identifies agroup that will be set as the current talk group by the second mobiledevice.
 12. The apparatus of claim 10, wherein the apparatus furthercomprises the second mobile device and wherein the second mobile deviceis configured to: receive the second set of one or more groupaffiliation parameters and group de-affiliation parameters; and modify ascan list maintained by the second mobile device based on the second setof one or more group affiliation parameters and group de-affiliationparameters.
 13. The apparatus of claim 12, wherein the second mobiledevice is configured to modify the scan list by deleting a group fromthe scan list.
 14. The apparatus of claim 13, wherein the apparatusfurther comprises the first mobile device and wherein the first mobiledevice is configured to maintain a scan list that comprises the groupdeleted from the scan list of the second mobile device.
 15. Theapparatus of claim 10, wherein the set of groups is a second set ofgroups, wherein the affiliation request is a second affiliation request,and wherein the at least one memory device is configured to store a setof instructions that, when executed by the processor, cause theprocessor to perform the following functions: receive a firstaffiliation request; determine the first set of one or more groupaffiliation parameters and group de-affiliation parameters, wherein thefirst set of one or more group affiliation parameters and groupde-affiliation parameters are associated with a first set of groups andwherein the first set of groups and the second set of groups have atleast one group in common; and in response to receiving the firstaffiliation request, convey, to the first mobile device, the first setof one or more group affiliation parameters and group de-affiliationparameters.
 16. An apparatus for implementing a group call in a wirelesscommunication system, the apparatus comprising: a Group ManagementServer comprising: a processor; and an at least one memory device thatis configured to store a set of instructions that, when executed by theprocessor, cause the processor to perform the following functions:receive a request to initiate a group call involving a group comprisinga first mobile device and a second mobile device of a same user; selectonly one of the first mobile device and the second mobile device toparticipate in the group call; and arrange for only the selected mobiledevice of the first mobile device and the second mobile device toparticipate in the group call.
 17. The apparatus of claim 16, whereinthe at least one memory device is configured to store a set ofinstructions that, when executed by the processor, cause the processorto arrange for only the selected mobile device to participate in thegroup call by: notifying only the selected mobile device, of the firstmobile device and the second mobile device, of the group call.
 18. Theapparatus of claim 16, wherein the at least one memory device isconfigured to store a set of instructions that, when executed by theprocessor, cause the processor to notify the first mobile device and thesecond mobile device of the group call and wherein the at least onememory device further is configured to store a set of instructions that,when executed by the processor, cause the processor to arrange for onlythe selected mobile device to participate in the group call byterminating a participation of a non-selected mobile device of the firstmobile device and the second mobile device.
 19. A method for controllinggroup affiliation in a wireless communication system, the methodcomprising: receiving, by a group management server from a first mobiledevice associated with a first user, a first affiliation request; inresponse to receiving the first affiliation request, conveying, to thefirst mobile device, a first set of one or more group affiliationparameters and group de-affiliation parameters; receiving, by a groupmanagement server from a second mobile device associated with the firstuser, a second affiliation request; in response to receiving the secondaffiliation request, modifying the first set of one or more groupaffiliation parameters and group de-affiliation parameters to produce amodified first set of one or more group affiliation parameters and groupde-affiliation parameters; and conveying, to the first mobile device,the modified first set of one or more group affiliation parameters andgroup de-affiliation parameters.